boost 1.68 #621
Open
boost 1.68 #621
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See also Issue #617.
As mentioned there, this should probably be provided under a different name for testing first.
I've run into some more problems:
boost built with --std=c++-14 seems to be most compatible, it can be used by both C++11 and C++17 programs. There seems to be no infrastructure for requiring a C++14-capable compiler, though, and I figured people would either use tigerbrew's most current gcc or they wouldn't.
there was a weird linking problem related to the interaction between
@loader_pathinstall names and symlinking.@loader_pathis supposed to be supported on 10.4, but it only worked when I copied the files directly to/usr/local/lib. So I patched boost not to set install names for its libraries.boost 1.69 changed the naming scheme for library files, and I don't understand how cmake is supposed to work with that. So this PR uses boost 1.68, and I'm waiting to see how things will work in present-day homebrew.